Document vm_today and datetime support in calculated fields #1167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of changes
vm_today,date,datetime,timedelta,relativedelta.vm_today(updates when formula re-runs)..isoformat()for dates).File touched:
site/guide/model-inventory/_field-types.qmd.Findings from codebase investigation
backend/src/backend/utils/code_executor.py): Execution environment injectsvm_today = date.today()and exposesdate,datetime,timedelta,relativedelta(and others) into formula scope. Date fields are passed as values that requireint(params.x) / 1000fordate.fromtimestamp()(JS/Python timestamp precision difference).vm_today).How to test
Open deploy preview → Model inventory → Field types → Calculation, expand "Example — Date arithmetic and vm_today" and confirm table + code blocks render.
[sc-7465]